Broadcasting of a non-terrestrial network system information block

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive, from an entity of a non-terrestrial network (NTN), a system information block (SIB) that indicates information relating to one or more NTN SIBs that are to include at least one of ephemeris information or feeder link timing advance information. The UE may receive, from the entity of the NTN, the one or more NTN SIBs based at least in part on the information. Numerous other aspects are described.

CROSS-REFERENCE TO RELATED APPLICATION

This Patent application claims priority to U.S. Provisional PatentApplication No. 63/203,961, filed on Aug. 5, 2021, entitled“BROADCASTING OF A NON-TERRESTRIAL NETWORK SYSTEM INFORMATION BLOCK,”and assigned to the assignee hereof. The disclosure of the priorApplication is considered part of and is incorporated by reference intothis Patent Application.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication and to techniques and apparatuses for broadcasting of anon-terrestrial network (NTN) system information block (SIB).

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency division multipleaccess (FDMA) systems, orthogonal frequency division multiple access(OFDMA) systems, single-carrier frequency division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless network may include one or more base stations that supportcommunication for a user equipment (UE) or multiple UEs. A UE maycommunicate with a base station via downlink communications and uplinkcommunications. “Downlink” (or “DL”) refers to a communication link fromthe base station to the UE, and “uplink” (or “UL”) refers to acommunication link from the UE to the base station.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent UEs to communicate on a municipal, national, regional, and/orglobal level. New Radio (NR), which may be referred to as 5G, is a setof enhancements to the LTE mobile standard promulgated by the 3GPP. NRis designed to better support mobile broadband internet access byimproving spectral efficiency, lowering costs, improving services,making use of new spectrum, and better integrating with other openstandards using orthogonal frequency division multiplexing (OFDM) with acyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/orsingle-carrier frequency division multiplexing (SC-FDM) (also known asdiscrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, aswell as supporting beamforming, multiple-input multiple-output (MIMO)antenna technology, and carrier aggregation. As the demand for mobilebroadband access continues to increase, further improvements in LTE, NR,and other radio access technologies remain useful.

SUMMARY

Some aspects described herein relate to a method of wirelesscommunication at a user equipment (UE). The method may includereceiving, from an entity of a non-terrestrial network (NTN), a systeminformation block (SIB) that indicates information relating to one ormore NTN SIBs that are to include at least one of ephemeris informationor feeder link timing advance information. The method may includereceiving, from the entity of the NTN, the one or more NTN SIBs based atleast in part on the information.

Some aspects described herein relate to a method of wirelesscommunication at an entity of an NTN. The method may includetransmitting, to a UE, a SIB that indicates information relating to oneor more NTN SIBs that are to include at least one of ephemerisinformation or feeder link timing advance information. The method mayinclude transmitting, to the UE, the one or more NTN SIBs based at leastin part on the information.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include a memory comprisinginstructions and one or more processors configured to execute theinstructions. The one or more processors may be configured to executethe instructions and cause the apparatus to obtain, from an entity of anNTN, a SIB that indicates information relating to one or more NTN SIBsthat are to include at least one of ephemeris information or feeder linktiming advance information. The one or more processors may be configuredto execute the instructions and cause the apparatus to obtain, from theentity of the NTN, the one or more NTN SIBs based at least in part onthe information.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include a memory comprisinginstructions and one or more processors configured to execute theinstructions. The one or more processors may be configured to executethe instructions and cause the apparatus to output for transmission to aUE a SIB that indicates information relating to one or more NTN SIBsthat are to include at least one of ephemeris information or feeder linktiming advance information. The one or more processors may be configuredto execute the instructions and cause the apparatus to output fortransmission to the UE the one or more NTN SIBs based at least in parton the information.

Some aspects described herein relate to a non-transitorycomputer-readable medium comprising instructions. The instructions, whenexecuted by one or more processors of an apparatus, may cause theapparatus to obtain, from an entity of an NTN, a SIB that indicatesinformation relating to one or more NTN SIBs that are to include atleast one of ephemeris information or feeder link timing advanceinformation. The instructions, when executed by one or more processorsof the apparatus, may cause the apparatus to obtain, from the entity ofthe NTN, the one or more NTN SIBs based at least in part on theinformation.

Some aspects described herein relate to a non-transitorycomputer-readable medium comprising instructions. The instructions, whenexecuted by one or more processors of an apparatus, may cause theapparatus to output for transmission to a UE a SIB that indicatesinformation relating to one or more NTN SIBs that are to include atleast one of ephemeris information or feeder link timing advanceinformation. The instructions, when executed by one or more processorsof the apparatus, may cause the apparatus to output for transmission tothe UE the one or more NTN SIBs based at least in part on theinformation.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for obtaining, from anentity of an NTN, a SIB that indicates information relating to one ormore NTN SIBs that are to include at least one of ephemeris informationor feeder link timing advance information. The apparatus may includemeans for obtaining, from the entity of the NTN, the one or more NTNSIBs based at least in part on the information.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for outputting fortransmission to a UE a SIB that indicates information relating to one ormore NTN SIBs that are to include at least one of ephemeris informationor feeder link timing advance information. The apparatus may includemeans for outputting for transmission to the UE the one or more NTN SIBsbased at least in part on the information.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, and/or processing system assubstantially described herein with reference to and as illustrated bythe drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages, will be betterunderstood from the following description when considered in connectionwith the accompanying figures. Each of the figures is provided for thepurposes of illustration and description, and not as a definition of thelimits of the claims.

While aspects are described in the present disclosure by illustration tosome examples, those skilled in the art will understand that suchaspects may be implemented in many different arrangements and scenarios.Techniques described herein may be implemented using different platformtypes, devices, systems, shapes, sizes, and/or packaging arrangements.For example, some aspects may be implemented via integrated chipembodiments or other non-module-component based devices (e.g., end-userdevices, vehicles, communication devices, computing devices, industrialequipment, retail/purchasing devices, medical devices, and/or artificialintelligence devices). Aspects may be implemented in chip-levelcomponents, modular components, non-modular components, non-chip-levelcomponents, device-level components, and/or system-level components.Devices incorporating described aspects and features may includeadditional components and features for implementation and practice ofclaimed and described aspects. For example, transmission and receptionof wireless signals may include one or more components for analog anddigital purposes (e.g., hardware components including antennas, radiofrequency (RF) chains, power amplifiers, modulators, buffers,processors, interleavers, adders, and/or summers). It is intended thataspects described herein may be practiced in a wide variety of devices,components, systems, distributed arrangements, and/or end-user devicesof varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a diagram illustrating an example of a wireless network, inaccordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a base station incommunication with a user equipment (UE) in a wireless network, inaccordance with the present disclosure.

FIG. 3 is a diagram illustrating an example of a regenerative satellitedeployment and an example of a transparent satellite deployment in anon-terrestrial network (NTN), in accordance with the presentdisclosure.

FIG. 4 is a diagram illustrating an example of system informationscheduling, in accordance with the present disclosure.

FIG. 5 is a diagram illustrating an example of transmission of anNTN-specific system information block (SIB), in accordance with thepresent disclosure.

FIG. 6 is a diagram illustrating an example associated with broadcastingof an NTN SIB, in accordance with the present disclosure.

FIGS. 7-8 are diagrams illustrating example processes associated withbroadcasting of an NTN SIB, in accordance with the present disclosure.

FIGS. 9-10 are diagrams of example apparatuses for wirelesscommunication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. One skilled in theart should appreciate that the scope of the disclosure is intended tocover any aspect of the disclosure disclosed herein, whether implementedindependently of or combined with any other aspect of the disclosure.For example, an apparatus may be implemented or a method may bepracticed using any number of the aspects set forth herein. In addition,the scope of the disclosure is intended to cover such an apparatus ormethod which is practiced using other structure, functionality, orstructure and functionality in addition to or other than the variousaspects of the disclosure set forth herein. It should be understood thatany aspect of the disclosure disclosed herein may be embodied by one ormore elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

While aspects may be described herein using terminology commonlyassociated with a 5G or New Radio (NR) radio access technology (RAT),aspects of the present disclosure can be applied to other RATs, such asa 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100,in accordance with the present disclosure. The wireless network 100 maybe or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g.,Long Term Evolution (LTE)) network, among other examples. The wirelessnetwork 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110 b, a BS 110 c, and a BS 110 d), a user equipment (UE) 120 ormultiple UEs 120 (shown as a UE 120 a, a UE 120 b, a UE 120 c, a UE 120d, and a UE 120 e), and/or other network entities. A base station 110 isan entity that communicates with UEs 120. A base station 110 (sometimesreferred to as a BS) may include, for example, an NR base station, anLTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G),an access point, and/or a transmission reception point (TRP). Each basestation 110 may provide communication coverage for a particulargeographic area. In the Third Generation Partnership Project (3GPP), theterm “cell” can refer to a coverage area of a base station 110 and/or abase station subsystem serving this coverage area, depending on thecontext in which the term is used.

A base station 110 may provide communication coverage for a macro cell,a pico cell, a femto cell, and/or another type of cell. A macro cell maycover a relatively large geographic area (e.g., several kilometers inradius) and may allow unrestricted access by UEs 120 with servicesubscriptions. A pico cell may cover a relatively small geographic areaand may allow unrestricted access by UEs 120 with service subscription.A femto cell may cover a relatively small geographic area (e.g., a home)and may allow restricted access by UEs 120 having association with thefemto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A basestation 110 for a macro cell may be referred to as a macro base station.A base station 110 for a pico cell may be referred to as a pico basestation. A base station 110 for a femto cell may be referred to as afemto base station or an in-home base station. In the example shown inFIG. 1 , the BS 110 a may be a macro base station for a macro cell 102a, the BS 110 b may be a pico base station for a pico cell 102 b, andthe BS 110 c may be a femto base station for a femto cell 102 c. A basestation may support one or multiple (e.g., three) cells.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of a basestation 110 that is mobile (e.g., a mobile base station). In someexamples, the base stations 110 may be interconnected to one anotherand/or to one or more other base stations 110 or network nodes (notshown) in the wireless network 100 through various types of backhaulinterfaces, such as a direct physical connection or a virtual network,using any suitable transport network.

In some aspects, as shown in FIG. 1 , a cell may be provided by a basestation 110 of a non-terrestrial network. As used herein,“non-terrestrial network” (NTN) may refer to a network for which accessis provided by a non-terrestrial base station, such as a base stationcarried by an NTN entity (e.g., satellite, a balloon, a dirigible, anairplane, an unmanned aerial vehicle, a high altitude platform station).A base station of the NTN may be a base station carried by the NTNentity (regenerative deployment) or a base station on the ground thatcommunicates via the NTN entity (bent-pipe or transparent deployment).

The wireless network 100 may include one or more relay stations. A relaystation is an entity that can receive a transmission of data from anupstream station (e.g., a base station 110 or a UE 120) and send atransmission of the data to a downstream station (e.g., a UE 120 or abase station 110). A relay station may be a UE 120 that can relaytransmissions for other UEs 120. In the example shown in FIG. 1 , the BS110 d (e.g., a relay base station) may communicate with the BS 110 a(e.g., a macro base station) and the UE 120 d in order to facilitatecommunication between the BS 110 a and the UE 120 d. A base station 110that relays communications may be referred to as a relay station, arelay base station, a relay, or the like.

The wireless network 100 may be a heterogeneous network that includesbase stations 110 of different types, such as macro base stations, picobase stations, femto base stations, relay base stations, or the like.These different types of base stations 110 may have different transmitpower levels, different coverage areas, and/or different impacts oninterference in the wireless network 100. For example, macro basestations may have a high transmit power level (e.g., 5 to 40 watts)whereas pico base stations, femto base stations, and relay base stationsmay have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to or communicate with a set of basestations 110 and may provide coordination and control for these basestations 110. The network controller 130 may communicate with the basestations 110 via a backhaul communication link. The base stations 110may communicate with one another directly or indirectly via a wirelessor wireline backhaul communication link.

The UEs 120 may be dispersed throughout the wireless network 100, andeach UE 120 may be stationary or mobile. A UE 120 may include, forexample, an access terminal, a terminal, a mobile station, and/or asubscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone),a personal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a laptop computer, a cordlessphone, a wireless local loop (WLL) station, a tablet, a camera, a gamingdevice, a netbook, a smartbook, an ultrabook, a medical device, abiometric device, a wearable device (e.g., a smart watch, smartclothing, smart glasses, a smart wristband, smart jewelry (e.g., a smartring or a smart bracelet)), an entertainment device (e.g., a musicdevice, a video device, and/or a satellite radio), a vehicular componentor sensor, a smart meter/sensor, industrial manufacturing equipment, aglobal positioning system device, and/or any other suitable device thatis configured to communicate via a wireless medium.

Some UEs 120 may be considered machine-type communication (MTC) orevolved or enhanced machine-type communication (eMTC) UEs. An MTC UEand/or an eMTC UE may include, for example, a robot, a drone, a remotedevice, a sensor, a meter, a monitor, and/or a location tag, that maycommunicate with a base station, another device (e.g., a remote device),or some other entity. Some UEs 120 may be considered Internet-of-Things(IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT)devices. Some UEs 120 may be considered a Customer Premises Equipment. AUE 120 may be included inside a housing that houses components of the UE120, such as processor components and/or memory components. In someexamples, the processor components and the memory components may becoupled together. For example, the processor components (e.g., one ormore processors) and the memory components (e.g., a memory) may beoperatively coupled, communicatively coupled, electronically coupled,and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in agiven geographic area. Each wireless network 100 may support aparticular RAT and may operate on one or more frequencies. A RAT may bereferred to as a radio technology, an air interface, or the like. Afrequency may be referred to as a carrier, a frequency channel, or thelike. Each frequency may support a single RAT in a given geographic areain order to avoid interference between wireless networks of differentRATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120 a and UE120 e) may communicate directly using one or more sidelink channels(e.g., without using a base station 110 as an intermediary tocommunicate with one another). For example, the UEs 120 may communicateusing peer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or amesh network. In such examples, a UE 120 may perform schedulingoperations, resource selection operations, and/or other operationsdescribed elsewhere herein as being performed by the base station 110.

Devices of the wireless network 100 may communicate using theelectromagnetic spectrum, which may be subdivided by frequency orwavelength into various classes, bands, channels, or the like. Forexample, devices of the wireless network 100 may communicate using oneor more operating bands. In 5G NR, two initial operating bands have beenidentified as frequency range designations FR1 (410 MHz-7.125 GHz) andFR2 (24.25 GHz-52.6 GHz). It should be understood that although aportion of FR1 is greater than 6 GHz, FR1 is often referred to(interchangeably) as a “Sub-6 GHz” band in various documents andarticles. A similar nomenclature issue sometimes occurs with regard toFR2, which is often referred to (interchangeably) as a “millimeter wave”band in documents and articles, despite being different from theextremely high frequency (EHF) band (30 GHz-300 GHz) which is identifiedby the International Telecommunications Union (ITU) as a “millimeterwave” band.

The frequencies between FR1 and FR2 are often referred to as mid-bandfrequencies. Recent 5G NR studies have identified an operating band forthese mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1characteristics and/or FR2 characteristics, and thus may effectivelyextend features of FR1 and/or FR2 into mid-band frequencies. Inaddition, higher frequency bands are currently being explored to extend5G NR operation beyond 52.6 GHz. For example, three higher operatingbands have been identified as frequency range designations FR4a or FR4-1(52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise,it should be understood that the term “sub-6 GHz” or the like, if usedherein, may broadly represent frequencies that may be less than 6 GHz,may be within FR1, or may include mid-band frequencies. Further, unlessspecifically stated otherwise, it should be understood that the term“millimeter wave” or the like, if used herein, may broadly representfrequencies that may include mid-band frequencies, may be within FR2,FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It iscontemplated that the frequencies included in these operating bands(e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified,and techniques described herein are applicable to those modifiedfrequency ranges.

In some aspects, the UE 120 may include a communication manager 140. Asdescribed in more detail elsewhere herein, the communication manager 140may obtain, from an entity of an NTN, a system information block (SIB)that indicates information relating to one or more NTN SIBs that are toinclude at least one of ephemeris information or feeder link timingadvance information; and obtain, from the entity of the NTN, the one ormore NTN SIBs based at least in part on the information. Additionally,or alternatively, the communication manager 140 may perform one or moreother operations described herein.

In some aspects, the base station 110, or another NTN entity, mayinclude a communication manager 150. As described in more detailelsewhere herein, the communication manager 150 may output fortransmission to a UE a SIB that indicates information relating to one ormore NTN SIBs that are to include at least one of ephemeris informationor feeder link timing advance information; and output for transmissionto the UE the one or more NTN SIBs based at least in part on theinformation. Additionally, or alternatively, the communication manager150 may perform one or more other operations described herein.

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1 .

FIG. 2 is a diagram illustrating an example 200 of a base station 110 incommunication with a UE 120 in a wireless network 100, in accordancewith the present disclosure. The base station 110 may be equipped with aset of antennas 234 a through 234 t, such as T antennas (T≥1). The UE120 may be equipped with a set of antennas 252 a through 252 r, such asR antennas (R≥1).

At the base station 110, a transmit processor 220 may receive data, froma data source 212, intended for the UE 120 (or a set of UEs 120). Thetransmit processor 220 may select one or more modulation and codingschemes (MCSs) for the UE 120 based at least in part on one or morechannel quality indicators (CQIs) received from that UE 120. The basestation 110 may process (e.g., encode and modulate) the data for the UE120 based at least in part on the MCS(s) selected for the UE 120 and mayprovide data symbols for the UE 120. The transmit processor 220 mayprocess system information (e.g., for semi-static resource partitioninginformation (SRPI)) and control information (e.g., CQI requests, grants,and/or upper layer signaling) and provide overhead symbols and controlsymbols. The transmit processor 220 may generate reference symbols forreference signals (e.g., a cell-specific reference signal (CRS) or ademodulation reference signal (DMRS)) and synchronization signals (e.g.,a primary synchronization signal (PSS) or a secondary synchronizationsignal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO)processor 230 may perform spatial processing (e.g., precoding) on thedata symbols, the control symbols, the overhead symbols, and/or thereference symbols, if applicable, and may provide a set of output symbolstreams (e.g., T output symbol streams) to a corresponding set of modems232 (e.g., T modems), shown as modems 232 a through 232 t. For example,each output symbol stream may be provided to a modulator component(shown as MOD) of a modem 232. Each modem 232 may use a respectivemodulator component to process a respective output symbol stream (e.g.,for OFDM) to obtain an output sample stream. Each modem 232 may furtheruse a respective modulator component to process (e.g., convert toanalog, amplify, filter, and/or upconvert) the output sample stream toobtain a downlink signal. The modems 232 a through 232 t may transmit aset of downlink signals (e.g., T downlink signals) via a correspondingset of antennas 234 (e.g., T antennas), shown as antennas 234 a through234 t.

At the UE 120, a set of antennas 252 (shown as antennas 252 a through252 r) may receive the downlink signals from the base station 110 and/orother base stations 110 and may provide a set of received signals (e.g.,R received signals) to a set of modems 254 (e.g., R modems), shown asmodems 254 a through 254 r. For example, each received signal may beprovided to a demodulator component (shown as DEMOD) of a modem 254.Each modem 254 may use a respective demodulator component to condition(e.g., filter, amplify, downconvert, and/or digitize) a received signalto obtain input samples. Each modem 254 may use a demodulator componentto further process the input samples (e.g., for OFDM) to obtain receivedsymbols. A MIMO detector 256 may obtain received symbols from the modems254, may perform MIMO detection on the received symbols if applicable,and may provide detected symbols. A receive processor 258 may process(e.g., demodulate and decode) the detected symbols, may provide decodeddata for the UE 120 to a data sink 260, and may provide decoded controlinformation and system information to a controller/processor 280. Theterm “controller/processor” may refer to one or more controllers, one ormore processors, or a combination thereof. A channel processor maydetermine a reference signal received power (RSRP) parameter, a receivedsignal strength indicator (RSSI) parameter, a reference signal receivedquality (RSRQ) parameter, and/or a CQI parameter, among other examples.In some examples, one or more components of the UE 120 may be includedin a housing 284.

The network controller 130 may include a communication unit 294, acontroller/processor 290, and a memory 292. The network controller 130may include, for example, one or more devices in a core network. Thenetwork controller 130 may communicate with the base station 110 via thecommunication unit 294.

One or more antennas (e.g., antennas 234 a through 234 t and/or antennas252 a through 252 r) may include, or may be included within, one or moreantenna panels, one or more antenna groups, one or more sets of antennaelements, and/or one or more antenna arrays, among other examples. Anantenna panel, an antenna group, a set of antenna elements, and/or anantenna array may include one or more antenna elements (within a singlehousing or multiple housings), a set of coplanar antenna elements, a setof non-coplanar antenna elements, and/or one or more antenna elementscoupled to one or more transmission and/or reception components, such asone or more components of FIG. 2 .

On the uplink, at the UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports that include RSRP, RSSI, RSRQ, and/or CQI) from thecontroller/processor 280. The transmit processor 264 may generatereference symbols for one or more reference signals. The symbols fromthe transmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by the modems 254 (e.g., for DFT-s-OFDM orCP-OFDM), and transmitted to the base station 110. In some examples, themodem 254 of the UE 120 may include a modulator and a demodulator. Insome examples, the UE 120 includes a transceiver. The transceiver mayinclude any combination of the antenna(s) 252, the modem(s) 254, theMIMO detector 256, the receive processor 258, the transmit processor264, and/or the TX MIMO processor 266. The transceiver may be used by aprocessor (e.g., the controller/processor 280) and the memory 282 toperform aspects of any of the methods described herein (e.g., withreference to FIGS. 6-10 ).

At the base station 110, the uplink signals from UE 120 and/or other UEsmay be received by the antennas 234, processed by the modem 232 (e.g., ademodulator component, shown as DEMOD, of the modem 232), detected by aMIMO detector 236 if applicable, and further processed by a receiveprocessor 238 to obtain decoded data and control information sent by theUE 120. The receive processor 238 may provide the decoded data to a datasink 239 and provide the decoded control information to thecontroller/processor 240. The base station 110 may include acommunication unit 244 and may communicate with the network controller130 via the communication unit 244. The base station 110 may include ascheduler 246 to schedule one or more UEs 120 for downlink and/or uplinkcommunications. In some examples, the modem 232 of the base station 110may include a modulator and a demodulator. In some examples, the basestation 110 includes a transceiver. The transceiver may include anycombination of the antenna(s) 234, the modem(s) 232, the MIMO detector236, the receive processor 238, the transmit processor 220, and/or theTX MIMO processor 230. The transceiver may be used by a processor (e.g.,the controller/processor 240) and the memory 242 to perform aspects ofany of the methods described herein (e.g., with reference to FIGS. 6-10).

The controller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, and/or any other component(s) ofFIG. 2 may perform one or more techniques associated with broadcastingof an NTN SIB, as described in more detail elsewhere herein. In someaspects, the NTN entity described herein is the base station 110, isincluded in the base station 110, or includes one or more components ofthe base station 110 shown in FIG. 2 . For example, thecontroller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, and/or any other component(s) ofFIG. 2 may perform or direct operations of, for example, process 700 ofFIG. 7 , process 800 of FIG. 8 , and/or other processes as describedherein. The memory 242 and the memory 282 may store data and programcodes for the base station 110 and the UE 120, respectively. In someexamples, the memory 242 and/or the memory 282 may include anon-transitory computer-readable medium storing one or more instructions(e.g., code and/or program code) for wireless communication. Forexample, the one or more instructions, when executed (e.g., directly, orafter compiling, converting, and/or interpreting) by one or moreprocessors of the base station 110 and/or the UE 120, may cause the oneor more processors, the UE 120, and/or the base station 110 to performor direct operations of, for example, process 700 of FIG. 7 , process800 of FIG. 8 , and/or other processes as described herein. In someexamples, executing instructions may include running the instructions,converting the instructions, compiling the instructions, and/orinterpreting the instructions, among other examples.

In some aspects, the UE 120 includes means for obtaining, from an entityof an NTN, a SIB that indicates information relating to one or more NTNSIBs that are to include at least one of ephemeris information or feederlink timing advance information; and/or means for obtaining, from theentity of the NTN, the one or more NTN SIBs based at least in part onthe information. The means for the UE 120 to perform operationsdescribed herein may include, for example, one or more of communicationmanager 140, antenna 252, modem 254, MIMO detector 256, receiveprocessor 258, transmit processor 264, TX MIMO processor 266,controller/processor 280, or memory 282.

In some aspects, the base station 110, or another NTN entity, includesmeans for outputting for transmission to a UE a SIB that indicatesinformation relating to one or more NTN SIBs that are to include atleast one of ephemeris information or feeder link timing advanceinformation; and/or means for outputting for transmission to the UE theone or more NTN SIBs based at least in part on the information. Themeans for the base station 110, or another NTN entity, to performoperations described herein may include, for example, one or more ofcommunication manager 150, transmit processor 220, TX MIMO processor230, modem 232, antenna 234, MIMO detector 236, receive processor 238,controller/processor 240, memory 242, or scheduler 246.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofthe controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2 .

FIG. 3 is a diagram illustrating an example 300 of a regenerativesatellite deployment and an example 310 of a transparent satellitedeployment in an NTN, in accordance with the present disclosure.

Example 300 shows a regenerative satellite deployment. In example 300, aUE 120 is served by a satellite 320 via a service link 330. For example,the satellite 320 may include a base station 110 (e.g., base station 110a) or a gNB. In some aspects, the satellite 320 may be referred to as anon-terrestrial base station, a regenerative repeater, or an on-boardprocessing repeater. In some aspects, the satellite 320 may demodulatean uplink radio frequency signal, and may modulate a baseband signalderived from the uplink radio signal to produce a downlink radiofrequency transmission. The satellite 320 may transmit the downlinkradio frequency signal on the service link 330. The satellite 320 mayprovide a cell that covers the UE 120.

Example 310 shows a transparent satellite deployment, which may also bereferred to as a bent-pipe satellite deployment. In example 310, a UE120 is served by a satellite 340 via the service link 330. The satellite340 may be a transparent satellite. The satellite 340 may relay a signalreceived from gateway 350 via a feeder link 360. For example, thesatellite may receive an uplink radio frequency transmission, and maytransmit a downlink radio frequency transmission without demodulatingthe uplink radio frequency transmission. In some aspects, the satellitemay frequency convert the uplink radio frequency transmission receivedon the service link 330 to a frequency of the uplink radio frequencytransmission on the feeder link 360, and may amplify and/or filter theuplink radio frequency transmission. In some aspects, the UEs 120 shownin example 300 and example 310 may be associated with a GlobalNavigation Satellite System (GNSS) capability or a Global PositioningSystem (GPS) capability, though not all UEs have such capabilities. Thesatellite 340 may provide a cell that covers the UE 120.

The service link 330 may include a link between the satellite 340 andthe UE 120, and may include one or more of an uplink or a downlink. Thefeeder link 360 may include a link between the satellite 340 and thegateway 350, and may include one or more of an uplink (e.g., from the UE120 to the gateway 350) or a downlink (e.g., from the gateway 350 to theUE 120). An uplink of the service link 330 may be indicated by referencenumber 330-U (not shown in FIG. 3 ) and a downlink of the service link330 may be indicated by reference number 330-D (not shown in FIG. 3 ).Similarly, an uplink of the feeder link 360 may be indicated byreference number 360-U (not shown in FIG. 3 ) and a downlink of thefeeder link 360 may be indicated by reference number 360-D (not shown inFIG. 3 ).

The feeder link 360 and the service link 330 may each experience Dopplereffects due to the movement of the satellites 320 and 340, andpotentially movement of a UE 120. These Doppler effects may besignificantly larger than in a terrestrial network. The Doppler effecton the feeder link 360 may be compensated for to some degree, but maystill be associated with some amount of uncompensated frequency error.Furthermore, the gateway 350 may be associated with a residual frequencyerror, and/or the satellite 320/340 may be associated with an on-boardfrequency error. These sources of frequency error may cause a receiveddownlink frequency at the UE 120 to drift from a target downlinkfrequency.

As indicated above, FIG. 3 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 3 .

FIG. 4 is a diagram illustrating an example 400 of system informationscheduling, in accordance with the present disclosure.

A base station may provide system information (SI) for UEs covered bythe base station. SI may include physical layer information (e.g., in amaster information block), access information (e.g., in a SIB type 1(SIB1)), and/or other information for communication between UEs and thebase station (e.g., in one or more other types of SIBs). One or moreSIBs may be carried in an SI message. For example, SIB1 may be carriedalone in an SI message, and one or more other SIBs may be carried inanother SI message.

An SI message carrying SIB1 may be transmitted at fixed time locations,which may facilitate identification of SIB1. In some examples, SIB1carries scheduling information for other SI messages, and the other SImessages are transmitted in non-overlapping scheduling windows (e.g.,scheduling windows that do not overlap each other or the window ofSIB1). Thus, when the UE receives, in a physical downlink controlchannel (PDCCH), downlink control information (DCI) identifying an SImessage, the UE may know which SI message is being scheduled based atleast in part on the scheduling windows as indicated by the schedulinginformation of SIB1.

The scheduling information of SIB1 may indicate an SI window length(e.g., si-WindowLength), which is a common parameter for SI messages.That is, the SI window length is the same for all scheduled SI messages.The SI window length may define the length of an SI window in which a UEcan expect a SIB message (e.g., which may carry one or multiple SIBs) tobe transmitted. A UE may use a particular formula to determine a timelocation of the start of an SI window. In an SI window, a UE may searcha PDCCH (e.g., perform decoding of control communications using an SIradio network temporary identifier (SI-RNTI)) to receive an SI message.The scheduling information in SIB1 also may indicate an SI periodicity(e.g., si-Periodicity), per SI message, that identifies a time gapbetween consecutive SI windows (e.g., each SI message may have aseparately configured SI periodicity).

A change to the information in an SI message may occur only after anupcoming boundary of an SI modification period (unless the SI message isfor an earthquake and tsunami warning system (ETWS), a commercial mobilealert system (CMAS), positioning assistance data, a SIB type 9 (SIB9),or the like). Multiple SI windows may occur between SI modificationboundaries for repetitions or retransmissions of an SI message (e.g.,without change to the information in the SI message).

As shown in FIG. 4 , a boundary of an SI modification period may bedefined by system frame number (SFN) values for which SFN mod m=0, wherem is the number of radio frames in an SI modification period. In someaspects, the value of m may be determined based on a configuredcoefficient value (e.g., modificationPeriodCoeff), which may have avalue of 2, 4, 8, or 16, and a default paging cycle (e.g., PagingCycle),which may have a value of 32, 64, 128, or 256 radio frames. For example,as shown, in cases where the configured coefficient value is two and thedefault paging cycle is 64 radio frames, the SI modification period mayinclude 128 radio frames (e.g., corresponding to 1.28 seconds).Continuing with the example, a new SIB1 can be acquired at SFN mod 128=0(e.g., after the SI modification period boundary). A UE may acquire anew SIB1, after an SI modification period boundary, if the UE receivesan SI update notification prior to the SI modification period boundary.If the UE receives the SI update notification, the UE may receive SIB1after the SI modification period to check for a change to SI schedulinginformation and/or a value tag (e.g., valueTag) parameter. In a casewhere a SIB1 stored by a UE is valid (i.e., a SIB1 change notificationis not received), all other SIBs (e.g., for scheduling and/or content)also may be considered as valid (e.g., not changed).

As shown in FIG. 4 , if three SI messages are scheduled, then an SIperiod may include three non-overlapping SI windows. SI may also betransmitted on demand of a UE, in which case an SI window may bepresent, but the SI message is not broadcast. Within an SI window, an SImessage may be transmitted one or more times. However, a SIB is includedin only a single SI message, and the SIB is included within the SImessage at most once.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 4 .

FIG. 5 is a diagram illustrating an example 500 of transmission of anNTN-specific SIB, in accordance with the present disclosure. TheNTN-specific SIB (which may be referred to herein as an NTN SIB) is aSIB that carries information for communication in an NTN. For example,the NTN SIB may carry ephemeris information and/or feeder link timingadvance information. The feeder link timing advance information mayindicate a round trip delay of a whole or a part of a feeder link thatis common to multiple UEs. An NTN SIB may be a new SIB type that can beindicated by a SIB type information parameter (e.g., SIB-TypeInfo) ofSIB1.

As shown in FIG. 5 , an SI window may have a length (w) of 160 slots,and an NTN SIB may be first among multiple scheduled SIBs (i.e., n=1 forthe NTN SIB). An SI periodicity (T) may be configured as a value from 80milliseconds (ms) to 5.12 seconds. As shown in FIG. 5 , a periodicityfor an SI message that includes an NTN SIB may be 640 ms (e.g., T=64radio frames). In other words, the NTN SIB may have updated ephemerisinformation and/or updated feeder link timing advance information every640 ms. Thus, as shown, a UE may acquire updated ephemeris informationand/or feeder link timing advance information (e.g., an updated NTN SIB)at SFN=0, SFN=64, or SFN=128, and so forth (e.g., where a slot number(α) for acquiring the updated NTN SIB is expressed as slot α=(n−1)w mod10).

However, if an SI modification period is greater than 640 ms (e.g.,m=128 radio frames, or 1.28 seconds, as shown), then an update of theNTN SIB every 640 ms is not possible in current wireless networks. Thus,a network should be enabled to update an NTN SIB without notifying a UE(e.g., via a SI update notification paging message). In other words, theNTN SIB may change without a change to a scheduling parameter for SI ora change to the version (e.g., systemInfoValueTag) of SIB1.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 5 .

Ephemeris information may describe a trajectory of a satellite in an NTN(e.g., the ephemeris information may include parameters such as areference time, or so-called “epoch time,” that specifies the time atwhich orbital parameters are taken, Keplerian orbital parameters such asa square root of a semi-major axis, an eccentricity, and/or aninclination angle, and/or perturbation parameters such as a mean motiondifference from a computed value, a rate of change of right ascensionand/or inclination, and/or amplitudes of one or more sine or cosineharmonic correction terms, among other examples). For example, ephemerisinformation may indicate a formula that can be used by a UE to predict aposition of the satellite over time. A maximum modification periodicityfor ephemeris information may be from 10 seconds to 60 seconds, and atransmission periodicity for ephemeris information may be less than onesecond (e.g., which may be determined based at least in part on aninitial access delay). A UE may determine when to read ephemerisinformation based at least in part on an uplink timing error budget ofthe UE and/or an ephemeris prediction error associated with the UE.

Feeder link timing advance information may indicate a timing advance tobe used by a UE due to a delay associated with a feeder link between agateway and a satellite of an NTN. Feeder link timing advanceinformation may indicate a feeder link timing advance without timingdrift (e.g., a timing advance value that does not account for timingdrift over time) or a feeder link timing advance with timing drift(e.g., a timing advance formula that accounts for timing drift overtime).

A modification periodicity for a feeder link timing advance withouttiming drift may be greater than 20 seconds (e.g., assuming a 0.5 msgranularity), and a transmission periodicity for a feeder link timingadvance without timing drift may be less than one second (e.g., whichmay be determined based at least in part on an initial access delay). AUE may read feeder link timing advance information, for a timing advancewithout timing drift, before an effective time of the information (e.g.,which may be delayed relative to a signaling time of the information).In some examples, feeder link timing advance information, for a timingadvance without timing drift, may indicate a formula that a UE can useto determine a timing advance, thereby reducing reading of feeder linktiming advance information by the UE (e.g., the formula may indicate anincrease from a common offset by one slot every 30 seconds).

A maximum modification periodicity for a feeder link timing advance withtiming drift may be from 10 seconds to 20 seconds in FR1 or from 2seconds to 5 seconds in FR2, and a transmission periodicity for a feederlink timing advance with timing drift may be less than one second (e.g.,which may be determined based at least in part on an initial accessdelay). A UE may read feeder link timing advance information immediatelyupon an update of the information if a common timing advance offset(e.g., without timing drift) is used. Otherwise, if timing drift isused, the UE may delay reading the information for a time period afterthe update of the information (however, prediction error of the UE maydeteriorate quickly beyond the time period).

As described above, an NTN SIB carrying ephemeris information and/ortiming advance information (e.g., with timing drift) should be updatedperiodically. An update periodicity for the NTN SIB may be constrainedby a need for a reference time (e.g., epoch time) update, which also maylead to an update of the contents of the NTN SIB. For example, areference time used by a UE should be a latest time relative toreception of a message in order to reduce prediction error (ephemerisprediction performed by a network may be more accurate than ephemerisprediction performed by a UE due to the network's use of sophisticatedprediction models). In some examples, a reference time (e.g., epochtime) may be implicitly indicated to a UE in order to reduce signalingoverhead. For example, the reference time may be based at least in parton a boundary of a downlink signal (e.g., for an NTN SIB).

In a case where ephemeris information is updated each SI period via anNTN SIB, repetitions of the NTN SIB may be transmitted within an SIperiod. Here, the repetitions of the NTN SIB within the SI period may beassociated with the same reference time. That is, a single referencetime may be used per SI period. A network may predict a position and/ora velocity of the satellite of the NTN at the reference time (e.g., atime at an end of a slot of a first transmission within a period leavingthe satellite) based at least in part on a latest GNSS read.

Accordingly, in an NTN, there are some SI parameters that are handleddifferently than terrestrial networks due to a need to periodicallyupdate the SI parameters as the position of a satellite changes relativeto the ground. For example, because ephemeris information is used todescribe the trajectory of a satellite in the sky, ephemeris informationis generally specific to an NTN and there are no ephemeris-like SIparameters in a terrestrial network. In another example, a feeder linktiming advance also may be based at least in part on a position of thesatellite, whereas a timing advance used in a terrestrial network doesnot need to account for movement of a satellite.

In general, when one or more SI parameters are updated, a UE istypically notified via a paging message, and the UE is then expected toreacquire one or more SIBs to refresh the one or more SI parameters.However, transmitting a paging message to inform the UE when SIparameters need to be updated may lead to signaling overhead, which maybe particularly problematic in an NTN due to large propagation delaysand/or satellite motion potentially resulting in frequent changes to theSI parameters. Moreover, SI parameters for an NTN, such as ephemerisinformation and feeder link timing advance information, may need to beupdated more frequently than an SI modification period permits. If suchSI parameters are not updated with the requisite frequency, a UE maylose synchronization with a base station or a satellite, communicationsto or from the UE may fail, or the like.

In some techniques and apparatuses described herein, schedulinginformation for an NTN SIB may be provided in a SIB (e.g., SIB1). Insome aspects, an update period for an NTN SIB, as well as transmissionwindows for an NTN SIB within an SI period may be indicated in SIB1. Insome aspects, SIB1 may include an indication of a validity durationand/or an accuracy of an NTN SIB. In some aspects, SIB1 may include aresource allocation and/or an MCS for an NTN SIB to avoid a need toschedule an NTN SIB via a PDCCH.

Techniques described herein enable updating of ephemeris informationand/or feeder link timing advance information without triggering an SIupdate procedure via a paging message. For example, a UE may acquireupdated ephemeris information and/or feeder link timing advanceinformation in accordance with the scheduling information in SIB1 andwithout notification to the UE via paging. In this way, signalingoverhead is reduced. Moreover, as described above, a UE may receive aresource allocation for an NTN SIB in SIB1, rather than via a PDCCH,thereby further reducing signaling overhead.

FIG. 6 is a diagram illustrating an example 600 associated withbroadcasting of an NTN SIB, in accordance with the present disclosure.As shown in FIG. 6 , example 600 includes communication between an NTNentity 605 and a UE 120. In some aspects, the NTN entity 605 and the UE120 may be included in a wireless network, such as wireless network 100(e.g., an NTN). In some aspects, the NTN entity 605 may be a basestation 110 of the NTN, a gateway 350 of the NTN, a satellite 320 of theNTN, a satellite 340 of the NTN, or the like.

As shown by reference number 610, the NTN entity 605 may transmit, andthe UE 120 may receive, a SIB that indicates information relating to oneor more NTN SIBs. As described herein, the NTN SIB(s) may include atleast one of ephemeris information or feeder link timing advanceinformation (e.g., for a timing advance with timing drift or a timingadvance without timing drift). In some aspects, the SIB that indicatesthe information also may carry access information. For example, the SIBthat indicates the information may be a SIB1.

In some aspects, the information relating to the one or more NTN SIBsmay indicate an update periodicity for the one or more NTN SIBs (e.g.,for an SI message that includes the one or more NTN SIBs) and/or mayindicate one or more transmission windows (also referred to herein asscheduling windows or SI windows) within an update period for the one ormore NTN SIBs (e.g., for an SI message that includes the one or more NTNSIBs). The update periodicity may be an SI periodicity, as describedherein, at which the ephemeris information and/or the feeder link timingadvance information is updated. An update period may be an SI period, asdescribed herein, that is defined by the update periodicity and thatincludes one or more transmission windows for repetitions orretransmissions of the one or more NTN SIBs (e.g., of an SI message thatincludes the one or more NTN SIBs). The SIB may indicate the informationrelating to the one or more NTN SIBs (e.g., the update periodicityand/or the transmission windows) separately from (e.g., using differentparameter types than) information relating to one or more non-NTN SIBs(e.g., an update periodicity and/or transmission windows) indicated inthe SIB.

In aspects where a PDCCH is used to schedule a physical downlink sharedchannel (PDSCH) communication of the NTN SIB(s), a transmission windowmay be for the NTN entity 605 to transmit, and the UE 120 to receive, aPDCCH communication that schedules the PDSCH communication (e.g., thetransmission window is for PDCCH decoding). In aspects where a PDCCH isnot used, a transmission window may be for the NTN entity 605 totransmit, and the UE 120 to receive, the PDSCH communication of the NTNSIB(s) (e.g., a PDSCH communication of the ephemeris information and/orthe feeder link timing advance information).

In some aspects, a default update periodicity (e.g., used if an updateperiodicity is not indicated) for the one or more NTN SIBs may be thesame as a periodicity (e.g., a default periodicity or an indicatedperiodicity in SIB1) for one or more non-NTN SIBs (e.g., a SIB type 2(SIB2), a SIB type 3 (SIB3), and so forth). In some aspects, one or morerepetitions of an NTN SIB, within an update period, may be associatedwith the same reference time (e.g., an epoch time, or the like). Forexample, SI messages of ephemeris information transmitted in a singleupdate period may use the same reference time. However, different SIBsor information elements transmitted within an update period may beassociated with different reference times.

In some aspects, a reference time for the NTN SIB(s) (e.g., for one ormore repetitions of an NTN SIB that are associated with the samereference time) may be based at least in part on a particular downlinktransmit timepoint (e.g., with respect to a satellite) within an updateperiod. For example, a reference time for SI messages of ephemerisinformation may be a particular downlink timepoint, within an updateperiod, at a satellite of the NTN. The downlink transmit timepoint usedfor the reference time may be configured, specified, or otherwiseprovisioned for the UE 120 to thereby enable implicit indication of thereference time to the UE 120, as described herein. The downlink transmittimepoint, for example if a transmission window is specified, may be anend of a last downlink slot of a PDSCH carrying an NTN SIB (e.g.,carrying the ephemeris information and/or the feeder link timing advanceinformation) of a first transmission window of an update period at thesatellite. The downlink transmit timepoint, for example if atransmission window is not specified, may be an end of a first downlinkslot of an update period at the satellite.

In some aspects, the information relating to the one or more NTN SIBsmay indicate a resource allocation and/or an MCS for reception of theNTN SIB(s) at the UE 120. In this way, the UE 120 can receive a PDSCHcommunication of the NTN SIB(s) based at least in part on the resourceallocation and/or the MCS indicated in the information, and a PDCCH doesnot need to be used to schedule the PDSCH communication. A time domainresource allocation, of the resource allocation, may be with respect to(e.g., referenced to) a start of a transmission window for the one ormore NTN SIBs. In some aspects, the information relating to the one ormore NTN SIBs may indicate a message size of the one or more NTN SIBs.For example, the information may include an indication of the messagesize if an NTN SIB may use a variable message size.

In some aspects, the information relating to the one or more NTN SIBsmay indicate a validity duration and/or an accuracy (e.g., referenced toa particular accuracy per sub-carrier spacing) of the one or more NTNSIBs. The validity duration and/or the accuracy may be indicated in aunit of the update period (e.g., indicated as a multiplier of the updateperiod). In some aspects, the information may indicate a first validityduration and/or a first accuracy of the ephemeris information and asecond validity duration and/or a second accuracy of the feeder linktiming advance information.

In some aspects, a mechanism (e.g., an si-Periodicity parameter in SIB1)for indicating scheduling information for one or more non-NTN SIBs(e.g., SIB2, SIB3, and so forth), as described herein, may also be usedto indicate scheduling information for one or more NTN SIBs. Forexample, the information relating to the one or more NTN SIBs mayindicate an update periodicity for the one or more NTN SIBs using aparameter type (e.g., an si-Periodicity parameter type) of the SIB thatis also used to indicate a periodicity for one or more non-NTN SIBs. Inother words, an update period for an NTN SIB may be defined (e.g., inSIB1) the same way as an SI period for another SIB. An update period mayhave a size that is small enough to accommodate a random access channel(RACH) delay. In some aspects, one or more SI windows (e.g., a first SIwindow and a third SI window of an SI period) may be specified ordefined for transmission of an NTN SIB.

In some aspects, the information relating to the one or more NTN SIBsmay indicate an identifier of an entry in a table stored by the UE 120.The table (e.g., a lookup table) may identify various combinations of anupdate periodicity for an NTN SIB, transmission windows within an updateperiod for an NTN SIB (e.g., a PDCCH or a PDSCH of the NTN SIB), a timedomain resource allocation for an NTN SIB, a frequency domain resourceallocation for an NTN SIB, an MCS for an NTN SIB, and/or a message sizeof an NTN SIB. Accordingly, the identifier may indicate, according tothe table, a particular combination of an update periodicity for an NTNSIB, transmission windows within an update period for an NTN SIB, a timedomain resource allocation for an NTN SIB, a frequency domain resourceallocation for an NTN SIB, an MCS for an NTN SIB, and/or a message sizeof an NTN SIB.

In some aspects, the one or more NTN SIBs may include a single NTN SIBthat includes the ephemeris information and the feeder link timingadvance information (e.g., the ephemeris information and the feeder linktiming advance information may be sent together in one NTN SIB). In someaspects, the one or more NTN SIBs may include multiple NTN SIBs thatrespectively include the ephemeris information and the feeder linktiming advance information (e.g., the ephemeris information may be sentin a first NTN SIB and the feeder link timing advance information may besent in a second NTN SIB).

In some aspects, if the feeder link timing advance information indicatesa feeder link timing advance with timing drift, then the informationrelating to the one or more NTN SIBs may provide respective indicationsof a validity duration and/or an accuracy for the ephemeris informationand the feeder link timing advance information (e.g., when the ephemerisinformation and the feeder link timing advance information are senttogether in one NTN SIB). For example, the information may indicate afirst validity duration and/or a first accuracy of the ephemerisinformation and a second validity duration and/or a second accuracy ofthe feeder link timing advance information, as described above. In someaspects, if the feeder link timing advance information indicates afeeder link timing advance without timing drift, then an updateperiodicity for the feeder link timing advance information may be basedat least in part on an update periodicity for the ephemeris information(e.g., when the ephemeris information and the feeder link timing advanceinformation are sent together in one NTN SIB). For example, the updateperiodicity for the feeder link timing advance information may beindicated in a unit of the update periodicity for the ephemerisinformation.

In some aspects, if the feeder link timing advance information indicatesa feeder link timing advance without timing drift, the informationrelating to the one or more NTN SIBs may indicate the feeder link timingadvance information (e.g., SIB1 indicates the feeder link timing advanceinformation, rather than such information being indicated in an NTNSIB). Here, an update to the feeder link timing advance information mayuse a system information update procedure, as described herein. In someaspects, if the feeder link timing advance information indicates afeeder link timing advance without timing drift, the informationrelating to the one or more NTN SIBs may indicate an update periodicityfor the feeder link timing advance information and/or an update periodfor the feeder link timing advance information (e.g., but may notindicate a validity duration and/or an accuracy for the feeder linktiming advance information).

In some aspects, if the feeder link timing advance information indicatesa feeder link timing advance without timing drift, an application time(e.g., by the UE 120) of the feeder link timing advance information maybe based at least in part on a last slot number (m) of a first PDSCHcommunication of the one or more NTN SIBs in an update period, or a lastslot number (m) of a first transmission window, of the one or moretransmission windows, in an update period, and a system schedulingoffset value (K_(offset)). For example, an application time of thefeeder link timing advance (e.g., a common offset) may be in uplink slotnumber m+K_(offset)+x, where x is a constant value, such as 1 or 2.

As described herein, an update periodicity for an NTN SIB may indicate aperiodicity at which the ephemeris information and/or the feeder linktiming advance information is updated. Thus, an update to the one ormore NTN SIBs may include the (updated) ephemeris information and/or thefeeder link timing advance information without triggering (e.g., isindependent of triggering) a system information update procedure. Thatis, the update does not trigger SIB modification and associated paging,as described herein.

As shown by reference number 615, the NTN entity 605 may transmit, andthe UE 120 may receive, the one or more NTN SIBs based at least in parton the information relating to the one or more NTN SIBs in the SIB(e.g., in SIB1). For example, the UE 120 may receive the one or more NTNSIBs in accordance with an indicated update periodicity (e.g., within anupdate period according to the update periodicity), one or moreindicated transmission windows, an indicated resource allocation and/orMCS, or the like. As described herein, in each update period (e.g., andwithout SI update notification paging), the UE 120 may receive one ormore updated NTN SIBs that include updated ephemeris information and/orupdated feeder link timing advance information.

As shown by reference number 620, the UE 120 and the NTN entity 605 maycommunicate based at least in part on the one or more NTN SIBs. That is,the UE 120 and the NTN entity 605 may communicate based at least in parton the ephemeris information and/or the feeder link timing advanceinformation. For example, the UE 120 may communicate with the NTN entity605 using the ephemeris information and/or the feeder link timingadvance information (e.g., in accordance with a reference time, avalidity duration, and/or an accuracy, as described herein).

As indicated above, FIG. 6 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 6 .

FIG. 7 is a diagram illustrating an example process 700 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 700 is an example where the UE (e.g., UE 120) performsoperations associated with broadcasting of an NTN SIB.

As shown in FIG. 7 , in some aspects, process 700 may include receiving,from an entity of an NTN, a SIB that indicates information relating toone or more NTN SIBs that are to include at least one of ephemerisinformation or feeder link timing advance information (block 710). Forexample, the UE (e.g., using communication manager 140 and/or receptioncomponent 902, depicted in FIG. 9 ) may receive, from an entity of anNTN, a SIB that indicates information relating to one or more NTN SIBsthat are to include at least one of ephemeris information or feeder linktiming advance information, as described above.

As further shown in FIG. 7 , in some aspects, process 700 may includereceiving, from the entity of the NTN, the one or more NTN SIBs based atleast in part on the information (block 720). For example, the UE (e.g.,using communication manager 140 and/or reception component 902, depictedin FIG. 9 ) may receive, from the entity of the NTN, the one or more NTNSIBs based at least in part on the information, as described above.

Process 700 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the information indicates at least one of an updateperiodicity for the one or more NTN SIBs or one or more transmissionwindows within an update period for the one or more NTN SIBs.

In a second aspect, alone or in combination with the first aspect, theone or more transmission windows are for reception of a PDCCHcommunication that schedules the one or more NTN SIBs.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the one or more transmission windows are forreception of a PDSCH communication of the one or more NTN SIBs.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, a default update periodicity for the one ormore NTN SIBs is the same as a periodicity for one or more non-NTN SIBs.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, one or more repetitions of an NTN SIB, of theone or more NTN SIBs, within an update period, are associated with asame reference time.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, a reference time for the one or more NTN SIBs isbased at least in part on a particular downlink transmit timepointwithin an update period.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the information indicates at least one of aresource allocation or an MCS for reception of the one or more NTN SIBs.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, a time domain resource allocation of theresource allocation is with respect to a start of a transmission windowfor the one or more NTN SIBs.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the information further indicates a message sizeof the one or more NTN SIBs.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the information indicates at least one of avalidity duration or an accuracy of the one or more NTN SIBs.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the information indicates an updateperiodicity for the one or more NTN SIBs using a parameter type of theSIB that is also used to indicate a periodicity for one or more non-NTNSIBs.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, an update to the one or more NTN SIBsincludes at least one of the ephemeris information or the feeder linktiming advance information without triggering a system informationupdate procedure.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the information indicates an identifierthat indicates, according to a table, one or more of an updateperiodicity for the one or more NTN SIBs, one or more transmissionwindows within an update period for the one or more NTN SIBs, a timedomain resource allocation for the one or more NTN SIBs, a frequencydomain resource allocation for the one or more NTN SIBs, an MCS, or amessage size of the one or more NTN SIBs.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the one or more NTN SIBs include asingle NTN SIB that includes the ephemeris information and the feederlink timing advance information.

In a fifteenth aspect, alone or in combination with one or more of thefirst through fourteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance with timing drift,and the information indicates at least one of a first validity durationor a first accuracy of the ephemeris information and at least one of asecond validity duration or a second accuracy of the feeder link timingadvance information.

In a sixteenth aspect, alone or in combination with one or more of thefirst through fifteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift,and an update periodicity for the feeder link timing advance informationis based at least in part on an update periodicity for the ephemerisinformation.

In a seventeenth aspect, alone or in combination with one or more of thefirst through sixteenth aspects, the one or more NTN SIBs includemultiple NTN SIBs that respectively include the ephemeris informationand the feeder link timing advance information.

In an eighteenth aspect, alone or in combination with one or more of thefirst through seventeenth aspects, the information indicates the feederlink timing advance information, and the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift.

In a nineteenth aspect, alone or in combination with one or more of thefirst through eighteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift,and the information indicates at least one of an update periodicity forthe feeder link timing advance information or an update period for thefeeder link timing advance information.

In a twentieth aspect, alone or in combination with one or more of thefirst through nineteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift,and an application time of the feeder link timing advance information isbased at least in part on a last slot number of a first PDSCHcommunication of the one or more NTN SIBS or a last slot number of afirst transmission window in an update period, and a system schedulingoffset value.

Although FIG. 7 shows example blocks of process 700, in some aspects,process 700 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 7 .Additionally, or alternatively, two or more of the blocks of process 700may be performed in parallel.

FIG. 8 is a diagram illustrating an example process 800 performed, forexample, by an NTN entity, in accordance with the present disclosure.Example process 800 is an example where the NTN entity (e.g., basestation 110, satellite 320, satellite 340, gateway 350, or the like)performs operations associated with broadcasting of an NTN SIB.

As shown in FIG. 8 , in some aspects, process 800 may includetransmitting, to a UE, a SIB that indicates information relating to oneor more NTN SIBs that are to include at least one of ephemerisinformation or feeder link timing advance information (block 810). Forexample, the NTN entity (e.g., using communication manager 150 and/ortransmission component 1004, depicted in FIG. 10 ) may transmit, to aUE, a SIB that indicates information relating to one or more NTN SIBsthat are to include at least one of ephemeris information or feeder linktiming advance information, as described above.

As further shown in FIG. 8 , in some aspects, process 800 may includetransmitting, to the UE, the one or more NTN SIBs based at least in parton the information (block 820). For example, the NTN entity (e.g., usingcommunication manager 150 and/or transmission component 1004, depictedin FIG. 10 ) may transmit, to the UE, the one or more NTN SIBs based atleast in part on the information, as described above.

Process 800 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the information indicates at least one of an updateperiodicity for the one or more NTN SIBs or one or more transmissionwindows within an update period for the one or more NTN SIBs.

In a second aspect, alone or in combination with the first aspect, theone or more transmission windows are for transmission of a PDCCHcommunication that schedules the one or more NTN SIBs.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the one or more transmission windows are fortransmission of a PDSCH communication of the one or more NTN SIBs.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, a default update periodicity for the one ormore NTN SIBs is the same as a periodicity for one or more non-NTN SIBs.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, one or more repetitions of an NTN SIB, of theone or more NTN SIBs, within an update period, are associated with asame reference time.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, a reference time for the one or more NTN SIBs isbased at least in part on a particular downlink transmit timepointwithin an update period.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the information indicates at least one of aresource allocation or an MCS for reception of the one or more NTN SIBs.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, a time domain resource allocation of theresource allocation is with respect to a start of a transmission windowfor the one or more NTN SIBs.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the information further indicates a message sizeof the one or more NTN SIBs.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the information indicates at least one of avalidity duration or an accuracy of the one or more NTN SIBs.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the information indicates an updateperiodicity for the one or more NTN SIBs using a parameter type of theSIB that is also used to indicate a periodicity for one or more non-NTNSIBs.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, an update to the one or more NTN SIBsincludes at least one of the ephemeris information or the feeder linktiming advance information without triggering a system informationupdate procedure.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the information indicates an identifierthat indicates, according to a table, one or more of an updateperiodicity for the one or more NTN SIBs, one or more transmissionwindows within an update period for the one or more NTN SIBs, a timedomain resource allocation for the one or more NTN SIBs, a frequencydomain resource allocation for the one or more NTN SIBs, an MCS, or amessage size of the one or more NTN SIBs.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the one or more NTN SIBs include asingle NTN SIB that includes the ephemeris information and the feederlink timing advance information.

In a fifteenth aspect, alone or in combination with one or more of thefirst through fourteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance with timing drift,and the information indicates at least one of a first validity durationor a first accuracy of the ephemeris information and at least one of asecond validity duration or a second accuracy of the feeder link timingadvance information.

In a sixteenth aspect, alone or in combination with one or more of thefirst through fifteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift,and an update periodicity for the feeder link timing advance informationis based at least in part on an update periodicity for the ephemerisinformation.

In a seventeenth aspect, alone or in combination with one or more of thefirst through sixteenth aspects, the one or more NTN SIBs includemultiple NTN SIBs that respectively include the ephemeris informationand the feeder link timing advance information.

In an eighteenth aspect, alone or in combination with one or more of thefirst through seventeenth aspects, the information indicates the feederlink timing advance information, and the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift.

In a nineteenth aspect, alone or in combination with one or more of thefirst through eighteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift,and the information indicates at least one of an update periodicity forthe feeder link timing advance information or an update period for thefeeder link timing advance information.

In a twentieth aspect, alone or in combination with one or more of thefirst through nineteenth aspects, the feeder link timing advanceinformation indicates a feeder link timing advance without timing drift,and an application time of the feeder link timing advance information isbased at least in part on a last slot number of a first PDSCHcommunication of the one or more NTN SIBS or a last slot number of afirst transmission window in an update period, and a system schedulingoffset value.

Although FIG. 8 shows example blocks of process 800, in some aspects,process 800 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 8 .Additionally, or alternatively, two or more of the blocks of process 800may be performed in parallel.

FIG. 9 is a diagram of an example apparatus 900 for wirelesscommunication. The apparatus 900 may be a UE, or a UE may include theapparatus 900. In some aspects, the apparatus 900 includes a receptioncomponent 902 and a transmission component 904, which may be incommunication with one another (for example, via one or more busesand/or one or more other components). As shown, the apparatus 900 maycommunicate with another apparatus 906 (such as a UE, a base station, oranother wireless communication device) using the reception component 902and the transmission component 904. As further shown, the apparatus 900may include the communication manager 140. The communication manager 140may include an SI component 908, among other examples.

In some aspects, the apparatus 900 may be configured to perform one ormore operations described herein in connection with FIG. 6 .Additionally, or alternatively, the apparatus 900 may be configured toperform one or more processes described herein, such as process 700 ofFIG. 7 , or a combination thereof. In some aspects, the apparatus 900and/or one or more components shown in FIG. 9 may include one or morecomponents of the UE described in connection with FIG. 2 . Additionally,or alternatively, one or more components shown in FIG. 9 may beimplemented within one or more components described in connection withFIG. 2 . Additionally, or alternatively, one or more components of theset of components may be implemented at least in part as software storedin a memory. For example, a component (or a portion of a component) maybe implemented as instructions or code stored in a non-transitorycomputer-readable medium and executable by a controller or a processorto perform the functions or operations of the component.

The reception component 902 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 906. The reception component 902may provide received communications to one or more other components ofthe apparatus 900. In some aspects, the reception component 902 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus900. In some aspects, the reception component 902 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the UE described in connection with FIG. 2 .

The transmission component 904 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 906. In some aspects, one or moreother components of the apparatus 900 may generate communications andmay provide the generated communications to the transmission component904 for transmission to the apparatus 906. In some aspects, thetransmission component 904 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 906. In some aspects, the transmission component 904may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described in connection with FIG. 2 . Insome aspects, the transmission component 904 may be co-located with thereception component 902 in a transceiver.

The reception component 902 may receive, from an entity of an NTN (e.g.,apparatus 906), a SIB that indicates information relating to one or moreNTN SIBS that are to include at least one of ephemeris information orfeeder link timing advance information. The reception component 902 mayreceive, from the entity of the NTN, the one or more NTN SIBS based atleast in part on the information. The reception component 902 and/or thetransmission component 904 may communicate with the NTN entity based atleast in part on the one or more NTN SIBS. The SI component 908 mayprocess, store, apply, or the like, SI (e.g., the ephemeris informationand/or the feeder link timing advance information) in the one or moreNTN SIBS.

In some examples, means for transmitting, outputting, or sending (ormeans for outputting for transmission) may include one or more antennas,a modulator, a transmit MIMO processor, a transmit processor, or acombination thereof, of the UE described above in connection with FIG. 2.

In some examples, means for receiving (or means for obtaining) mayinclude one or more antennas, a demodulator, a MIMO detector, a receiveprocessor, or a combination thereof, of the UE described above inconnection with FIG. 2 .

In some cases, rather than actually transmitting, for example, signalsand/or data, a device may have an interface to output signals and/ordata for transmission (a means for outputting). For example, a processormay output signals and/or data, via a bus interface, to an RF front endfor transmission. Similarly, rather than actually receiving signalsand/or data, a device may have an interface to obtain the signals and/ordata received from another device (a means for obtaining). For example,a processor may obtain (or receive) the signals and/or data, via a businterface, from an RF front end for reception. In various aspects, an RFfront end may include various components, including transmit and receiveprocessors, transmit and receive MIMO processors, modulators,demodulators, and the like, such as depicted in the examples in FIG. 2 .

In some examples, means for determining, means for obtaining, or meansfor sending may include various processing system components, such as areceive processor, a transmit processor, a controller/processor, amemory, or a combination thereof, of the UE described above inconnection with FIG. 2 .

The number and arrangement of components shown in FIG. 9 are provided asan example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 9 . Furthermore, two or more components shownin FIG. 9 may be implemented within a single component, or a singlecomponent shown in FIG. 9 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 9 may perform one or more functions describedas being performed by another set of components shown in FIG. 9 .

FIG. 10 is a diagram of an example apparatus 1000 for wirelesscommunication. The apparatus 1000 may be a base station or another NTNentity, or a base station or another NTN entity may include theapparatus 1000. In some aspects, the apparatus 1000 includes a receptioncomponent 1002 and a transmission component 1004, which may be incommunication with one another (for example, via one or more busesand/or one or more other components). As shown, the apparatus 1000 maycommunicate with another apparatus 1006 (such as a UE, a base station,or another wireless communication device) using the reception component1002 and the transmission component 1004. As further shown, theapparatus 1000 may include the communication manager 150. Thecommunication manager 150 may include an SI component 1008, among otherexamples.

In some aspects, the apparatus 1000 may be configured to perform one ormore operations described herein in connection with FIG. 6 .Additionally, or alternatively, the apparatus 1000 may be configured toperform one or more processes described herein, such as process 800 ofFIG. 8 , or a combination thereof. In some aspects, the apparatus 1000and/or one or more components shown in FIG. 10 may include one or morecomponents of the base station described in connection with FIG. 2 .Additionally, or alternatively, one or more components shown in FIG. 10may be implemented within one or more components described in connectionwith FIG. 2 . Additionally, or alternatively, one or more components ofthe set of components may be implemented at least in part as softwarestored in a memory. For example, a component (or a portion of acomponent) may be implemented as instructions or code stored in anon-transitory computer-readable medium and executable by a controlleror a processor to perform the functions or operations of the component.

The reception component 1002 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1006. The reception component1002 may provide received communications to one or more other componentsof the apparatus 1000. In some aspects, the reception component 1002 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus1000. In some aspects, the reception component 1002 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the base station described in connection with FIG. 2 .

The transmission component 1004 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1006. In some aspects, one or moreother components of the apparatus 1000 may generate communications andmay provide the generated communications to the transmission component1004 for transmission to the apparatus 1006. In some aspects, thetransmission component 1004 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1006. In some aspects, the transmission component 1004may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the base station described in connection withFIG. 2 . In some aspects, the transmission component 1004 may beco-located with the reception component 1002 in a transceiver.

The transmission component 1004 may transmit, to a UE (e.g., apparatus1006), a SIB that indicates information relating to one or more NTN SIBSthat are to include at least one of ephemeris information or feeder linktiming advance information. The transmission component 1004 maytransmit, to the UE, the one or more NTN SIBs based at least in part onthe information. The reception component 1002 and/or the transmissioncomponent 1004 may communicate with the UE based at least in part on theone or more NTN SIBs. The SI component 1008 may generate, process,store, or the like SI (e.g., the ephemeris information and/or the feederlink timing advance information) for the one or more NTN SIBs.

In some examples, means for transmitting, outputting, or sending (ormeans for outputting for transmission) may include one or more antennas,a modulator, a transmit MIMO processor, a transmit processor, or acombination thereof, of the base station or another NTN entity describedabove in connection with FIG. 2 .

In some examples, means for receiving (or means for obtaining) mayinclude one or more antennas, a demodulator, a MIMO detector, a receiveprocessor, or a combination thereof, of the base station or another NTNentity described above in connection with FIG. 2 .

In some cases, rather than actually transmitting, for example, signalsand/or data, a device may have an interface to output signals and/ordata for transmission (a means for outputting). For example, a processormay output signals and/or data, via a bus interface, to an RF front endfor transmission. Similarly, rather than actually receiving signalsand/or data, a device may have an interface to obtain the signals and/ordata received from another device (a means for obtaining). For example,a processor may obtain (or receive) the signals and/or data, via a businterface, from an RF front end for reception. In various aspects, an RFfront end may include various components, including transmit and receiveprocessors, transmit and receive MIMO processors, modulators,demodulators, and the like, such as depicted in the examples in FIG. 2 .

In some examples, means for determining, means for obtaining, or meansfor sending may include various processing system components, such as areceive processor, a transmit processor, a controller/processor, amemory, or a combination thereof, of the base station or another NTNentity described above in connection with FIG. 2 .

The number and arrangement of components shown in FIG. 10 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 10 . Furthermore, two or more components shownin FIG. 10 may be implemented within a single component, or a singlecomponent shown in FIG. 10 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 10 may perform one or more functions describedas being performed by another set of components shown in FIG. 10 .

The following provides an overview of some Aspects of the presentdisclosure:

Aspect 1: A method of wireless communication at a user equipment (UE),comprising: obtaining, from an entity of a non-terrestrial network(NTN), a system information block (SIB) that indicates informationrelating to one or more NTN SIBs that are to include at least one ofephemeris information or feeder link timing advance information; andobtaining, from the entity of the NTN, the one or more NTN SIBs based atleast in part on the information.

Aspect 2: The method of Aspect 1, wherein the information indicates atleast one of an update periodicity for the one or more NTN SIBs or oneor more transmission windows within an update period for the one or moreNTN SIBs.

Aspect 3: The method of Aspect 2, wherein the one or more transmissionwindows are for reception of a physical downlink control channelcommunication that schedules the one or more NTN SIBs.

Aspect 4: The method of Aspect 2, wherein the one or more transmissionwindows are for reception of a physical downlink shared channelcommunication of the one or more NTN SIBs.

Aspect 5: The method of any of Aspects 1-4, wherein a default updateperiodicity for the one or more NTN SIBs is the same as a periodicityfor one or more non-NTN SIBs.

Aspect 6: The method of any of Aspects 1-5, wherein one or morerepetitions of an NTN SIB, of the one or more NTN SIBs, within an updateperiod, are associated with a same reference time.

Aspect 7: The method of any of Aspects 1-6, wherein a reference time forthe at least one of the ephemeris information or the feeder link timingadvance information of the one or more NTN SIBs is based at least inpart on a particular downlink transmit timepoint within an updateperiod.

Aspect 8: The method of any of Aspects 1-7, wherein the informationindicates at least one of a resource allocation or a modulation andcoding scheme for reception of the one or more NTN SIBs.

Aspect 9: The method of Aspect 8, wherein a time domain resourceallocation of the resource allocation is with respect to a start of atransmission window for the one or more NTN SIBs.

Aspect 10: The method of any of Aspects 8-9, wherein the informationfurther indicates a message size of the one or more NTN SIBs.

Aspect 11: The method of any of Aspects 1-10, wherein the informationindicates at least one of a validity duration or an accuracy of the oneor more NTN SIBs.

Aspect 12: The method of any of Aspects 1 or 5-11, wherein theinformation indicates an update periodicity for the one or more NTN SIBsusing a parameter type of the SIB that is also used to indicate aperiodicity for one or more non-NTN SIBs.

Aspect 13: The method of any of Aspects 1-11, wherein an update to theat least one of the ephemeris information or the feeder link timingadvance information is independent of triggering a system informationupdate procedure.

Aspect 14: The method of any of Aspects 1, 5-11, or 13, wherein theinformation indicates an identifier that indicates, according to atable, one or more of an update periodicity for the one or more NTNSIBs, one or more transmission windows within an update period for theone or more NTN SIBs, a time domain resource allocation for the one ormore NTN SIBs, a frequency domain resource allocation for the one ormore NTN SIBs, a modulation and coding scheme, or a message size of theone or more NTN SIBs.

Aspect 15: The method of any of Aspects 1-14, wherein the one or moreNTN SIBs include a single NTN SIB that includes the ephemerisinformation and the feeder link timing advance information.

Aspect 16: The method of Aspect 15, wherein the feeder link timingadvance information indicates a feeder link timing advance with timingdrift, and wherein the information indicates at least one of a firstvalidity duration or a first accuracy of the ephemeris information andat least one of a second validity duration or a second accuracy of thefeeder link timing advance information.

Aspect 17: The method of Aspect 15, wherein the feeder link timingadvance information indicates a feeder link timing advance withouttiming drift, and wherein an update periodicity for the feeder linktiming advance information is based at least in part on an updateperiodicity for the ephemeris information.

Aspect 18: The method of any of Aspects 1-14, wherein the one or moreNTN SIBs include multiple NTN SIBs that respectively include theephemeris information and the feeder link timing advance information.

Aspect 19: The method of any of Aspects 1-14, wherein the informationindicates the feeder link timing advance information, and the feederlink timing advance information indicates a feeder link timing advancewithout timing drift.

Aspect 20: The method of any of Aspects 1-15 or 17-18, wherein thefeeder link timing advance information indicates a feeder link timingadvance without timing drift, and wherein the information indicates atleast one of an update periodicity for the feeder link timing advanceinformation or an update period for the feeder link timing advanceinformation.

Aspect 21: The method of any of Aspects 1-15, 17-18, or 20, wherein thefeeder link timing advance information indicates a feeder link timingadvance without timing drift, and wherein an application time of thefeeder link timing advance information is based at least in part on alast slot number of a first physical downlink shared channelcommunication of the one or more NTN SIBs or a last slot number of afirst transmission window in an update period, and a system schedulingoffset value.

Aspect 22: A method of wireless communication at an entity of anon-terrestrial network (NTN), comprising: outputting for transmissionto a user equipment (UE) a system information block (SIB) that indicatesinformation relating to one or more NTN SIBs that are to include atleast one of ephemeris information or feeder link timing advanceinformation; and outputting for transmission to the UE, the one or moreNTN SIBs based at least in part on the information.

Aspect 23: The method of Aspect 22, wherein the information indicates atleast one of an update periodicity for the one or more NTN SIBs or oneor more transmission windows within an update period for the one or moreNTN SIBs.

Aspect 24: The method of Aspect 23, wherein the one or more transmissionwindows are for transmission of a physical downlink control channelcommunication that schedules the one or more NTN SIBs.

Aspect 25: The method of Aspect 23, wherein the one or more transmissionwindows are for transmission of a physical downlink shared channelcommunication of the one or more NTN SIBs.

Aspect 26: The method of any of Aspects 22-25, wherein a default updateperiodicity for the one or more NTN SIBs is the same as a periodicityfor one or more non-NTN SIBs.

Aspect 27: The method of any of Aspects 22-26, wherein one or morerepetitions of an NTN SIB, of the one or more NTN SIBs, within an updateperiod, are associated with a same reference time.

Aspect 28: The method of any of Aspects 22-27, wherein a reference timefor the at least one of the ephemeris information or the feeder linktiming advance information of the one or more NTN SIBs is based at leastin part on a particular downlink transmit timepoint within an updateperiod.

Aspect 29: The method of any of Aspects 22-28, wherein the informationindicates at least one of a resource allocation or a modulation andcoding scheme for reception of the one or more NTN SIBs.

Aspect 30: The method of Aspect 29, wherein a time domain resourceallocation of the resource allocation is with respect to a start of atransmission window for the one or more NTN SIBS.

Aspect 31: The method of any of Aspects 29-30, wherein the informationfurther indicates a message size of the one or more NTN SIBs.

Aspect 32: The method of any of Aspects 22-31, wherein the informationindicates at least one of a validity duration or an accuracy of the oneor more NTN SIBs.

Aspect 33: The method of any of Aspects 22 or 26-32, wherein theinformation indicates an update periodicity for the one or more NTN SIBsusing a parameter type of the SIB that is also used to indicate aperiodicity for one or more non-NTN SIBS.

Aspect 34: The method of any of Aspects 22-32, wherein an update to theat least one of the ephemeris information or the feeder link timingadvance information is independent of triggering a system informationupdate procedure.

Aspect 35: The method of any of Aspects 22, 26-32, or 34 wherein theinformation indicates an identifier that indicates, according to atable, one or more of an update periodicity for the one or more NTNSIBs, one or more transmission windows within an update period for theone or more NTN SIBs, a time domain resource allocation for the one ormore NTN SIBs, a frequency domain resource allocation for the one ormore NTN SIBs, a modulation and coding scheme, or a message size of theone or more NTN SIBs.

Aspect 36: The method of any of Aspects 22-35, wherein the one or moreNTN SIBs include a single NTN SIB that includes the ephemerisinformation and the feeder link timing advance information.

Aspect 37: The method of Aspect 36, wherein the feeder link timingadvance information indicates a feeder link timing advance with timingdrift, and wherein the information indicates at least one of a firstvalidity duration or a first accuracy of the ephemeris information andat least one of a second validity duration or a second accuracy of thefeeder link timing advance information.

Aspect 38: The method of Aspect 36, wherein the feeder link timingadvance information indicates a feeder link timing advance withouttiming drift, and wherein an update periodicity for the feeder linktiming advance information is based at least in part on an updateperiodicity for the ephemeris information.

Aspect 39: The method of any of Aspects 22-35, wherein the one or moreNTN SIBs include multiple NTN SIBs that respectively include theephemeris information and the feeder link timing advance information.

Aspect 40: The method of any of Aspects 22-35, wherein the informationindicates the feeder link timing advance information, and the feederlink timing advance information indicates a feeder link timing advancewithout timing drift.

Aspect 41: The method of any of Aspects 22-36 or 38-39, wherein thefeeder link timing advance information indicates a feeder link timingadvance without timing drift, and wherein the information indicates atleast one of an update periodicity for the feeder link timing advanceinformation or an update period for the feeder link timing advanceinformation.

Aspect 42: The method of any of Aspects 22-36, 38-39, or 41, wherein thefeeder link timing advance information indicates a feeder link timingadvance without timing drift, and wherein an application time of thefeeder link timing advance information is based at least in part on alast slot number of a first physical downlink shared channelcommunication of the one or more NTN SIBS or a last slot number of afirst transmission window in an update period, and a system schedulingoffset value.

Aspect 43: An apparatus for wireless communication comprising a memorycomprising instructions and one or more processors configured to executethe instructions and cause the apparatus to perform the method of one ormore of Aspects 1-21.

Aspect 44: A user equipment (UE), comprising at least one receiver, amemory comprising instructions, and one or more processors configured toexecute the instructions and cause the UE to perform the method of oneor more of Aspects 1-21, wherein the at least one receiver is configuredto receive the SIB and the one or more NTN SIBs.

Aspect 45: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 1-21.

Aspect 46: A non-transitory computer-readable medium comprising one ormore instructions that, when executed by one or more processors of anapparatus, cause the apparatus to perform the method of one or more ofAspects 1-21.

Aspect 47: An apparatus for wireless communication comprising a memorycomprising instructions and one or more processors configured to executethe instructions and cause the apparatus to perform the method of one ormore of Aspects 22-42.

Aspect 48: An entity of a non-terrestrial network (NTN), comprising atleast one transmitter, a memory comprising instructions, and one or moreprocessors configured to execute the instructions and cause the entityof the NTN to perform the method of one or more of Aspects 22-42,wherein the at least one transmitter is configured to transmit the SIBand the one or more NTN SIBs.

Aspect 49: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 22-42.

Aspect 50: A non-transitory computer-readable medium comprising one ormore instructions that, when executed by one or more processors of anapparatus, cause the apparatus to perform the method of one or more ofAspects 22-42.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the aspects to the preciseforms disclosed. Modifications and variations may be made in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware and/or a combination of hardware and software. “Software”shall be construed broadly to mean instructions, instruction sets, code,code segments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,and/or functions, among other examples, whether referred to as software,firmware, middleware, microcode, hardware description language, orotherwise. As used herein, a “processor” is implemented in hardwareand/or a combination of hardware and software. It will be apparent thatsystems and/or methods described herein may be implemented in differentforms of hardware and/or a combination of hardware and software. Theactual specialized control hardware or software code used to implementthese systems and/or methods is not limiting of the aspects. Thus, theoperation and behavior of the systems and/or methods are describedherein without reference to specific software code, since those skilledin the art will understand that software and hardware can be designed toimplement the systems and/or methods based, at least in part, on thedescription herein.

As used herein, “satisfying a threshold” may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. Many of thesefeatures may be combined in ways not specifically recited in the claimsand/or disclosed in the specification. The disclosure of various aspectsincludes each dependent claim in combination with every other claim inthe claim set. As used herein, a phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination withmultiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b,a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b,and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterms “set” and “group” are intended to include one or more items andmay be used interchangeably with “one or more.” Where only one item isintended, the phrase “only one” or similar language is used. Also, asused herein, the terms “has,” “have,” “having,” or the like are intendedto be open-ended terms that do not limit an element that they modify(e.g., an element “having” A may also have B). Further, the phrase“based on” is intended to mean “based, at least in part, on” unlessexplicitly stated otherwise. Also, as used herein, the term “or” isintended to be inclusive when used in a series and may be usedinterchangeably with “and/or,” unless explicitly stated otherwise (e.g.,if used in combination with “either” or “only one of”).

What is claimed is:
 1. An apparatus for wireless communication,comprising: a memory comprising instructions; and one or more processorsconfigured to execute the instructions and cause the apparatus to:obtain, from an entity of a non-terrestrial network (NTN), a systeminformation block (SIB) that indicates information relating to one ormore NTN SIBs that are to include at least one of ephemeris informationor feeder link timing advance information; obtain, from the entity ofthe NTN, the one or more NTN SIBs based at least in part on theinformation, wherein at least one of: a reference time for the at leastone of the ephemeris information or the feeder link timing advanceinformation to be included in the one or more NTN SIBs is based at leastin part on a particular downlink transmit timepoint, the informationindicates at least one of a resource allocation for obtaining the one ormore NTN SIBs, a modulation and coding scheme for obtaining the one ormore NTN SIBs, a message size of the one or more NTN SIBs, a validityduration of the one or more NTN SIBs, or an accuracy of the one or moreNTN SIBs, an update to the at least one of the ephemeris information orthe feeder link timing advance information is independent of triggeringa system information update procedure, the one or more NTN SIBs includea single NTN SIB that includes the ephemeris information and the feederlink timing advance information, the feeder link timing advanceinformation indicates one of a feeder link timing advance with timingdrift or a feeder link timing advance without timing drift, or theinformation indicates the feeder link timing advance information; andthe feeder link timing advance information indicates the feeder linktiming advance without timing drift; and communicate with the entity ofthe NTN based at least in part on the one or more NTN SIBs.
 2. Theapparatus of claim 1, wherein the information indicates at least one ofan update periodicity for the one or more NTN SIBs or one or moretransmission windows within an update period for the one or more NTNSIBs.
 3. The apparatus of claim 2, wherein the one or more transmissionwindows are for reception of at least one of a physical downlink controlchannel communication that schedules the one or more NTN SIBs or aphysical downlink shared channel communication of the one or more NTNSIBs.
 4. The apparatus of claim 1, wherein one or more repetitions of anNTN SIB, of the one or more NTN SIBs, within an update period, areassociated with a same reference time.
 5. The apparatus of claim 1,wherein the reference time for the at least one of the ephemerisinformation or the feeder link timing advance information is based atleast in part on the particular downlink transmit timepoint within anupdate period.
 6. The apparatus of claim 1, wherein the informationindicates the at least one of the resource allocation for obtaining theone or more NTN SIBs, the modulation and coding scheme for obtaining theone or more NTN SIBs, the message size of the one or more NTN SIBs, thevalidity duration of the one or more NTN SIBs, or the accuracy of theone or more NTN SIBs.
 7. The apparatus of claim 1, wherein theinformation indicates an update periodicity for the one or more NTN SIBsusing a parameter type of the SIB.
 8. The apparatus of claim 1, whereinthe update to the at least one of the ephemeris information or thefeeder link timing advance information is independent of triggering thesystem information update procedure.
 9. The apparatus of claim 1,wherein the information indicates an identifier that indicates,according to a table, one or more of an update periodicity for the oneor more NTN SIBs, one or more transmission windows within an updateperiod for the one or more NTN SIBs, a time domain resource allocationfor the one or more NTN SIBs, a frequency domain resource allocation forthe one or more NTN SIBs, the modulation and coding scheme, and themessage size of the one or more NTN SIBs.
 10. The apparatus of claim 1,wherein the one or more NTN SIBs include the single NTN SIB thatincludes the ephemeris information and the feeder link timing advanceinformation.
 11. The apparatus of claim 1, wherein the feeder linktiming advance information indicates one of the feeder link timingadvance with timing drift or the feeder link timing advance withouttiming drift.
 12. The apparatus of claim 1, wherein the informationindicates the feeder link timing advance information, and the feederlink timing advance information indicates the feeder link timing advancewithout timing drift.
 13. The apparatus of claim 1, wherein the feederlink timing advance information indicates the feeder link timing advancewithout timing drift, and wherein the information indicates at least oneof an update periodicity for the feeder link timing advance informationor an update period for the feeder link timing advance information. 14.The apparatus of claim 1, wherein the feeder link timing advanceinformation indicates the feeder link timing advance without timingdrift, and wherein an application time of the feeder link timing advanceinformation is based at least in part on a last slot number of a firstphysical downlink shared channel communication of the one or more NTNSIBs or a last slot number of a first transmission window in an updateperiod, and a system scheduling offset value.
 15. The apparatus of claim1, further comprising: a receiver configured to receive the SIB and theone or more NTN SIBs, wherein the apparatus is configured as a userequipment (UE).
 16. An apparatus for wireless communication, comprising:a memory comprising instructions; and one or more processors configuredto execute the instructions and cause the apparatus to: output fortransmission to a user equipment (UE) a system information block (SIB)that indicates information relating to one or more non-terrestrialnetwork (NTN) SIBs that are to include at least one of ephemerisinformation or feeder link timing advance information; output fortransmission to the UE the one or more NTN SIBs based at least in parton the information, wherein at least one of: a reference time for the atleast one of the ephemeris information or the feeder link timing advanceinformation to be included in the one or more NTN SIBs is based at leastin part on a particular downlink transmit timepoint, the informationindicates at least one of a resource allocation for obtaining the one ormore NTN SIBs, a modulation and coding scheme for obtaining the one ormore NTN SIBs, a message size of the one or more NTN SIBs, a validityduration of the one or more NTN SIBs, or an accuracy of the one or moreNTN SIBs, an update to the at least one of the ephemeris information orthe feeder link timing advance information is independent of triggeringa system information update procedure, the one or more NTN SIBs includea single NTN SIB that includes the ephemeris information and the feederlink timing advance information, the feeder link timing advanceinformation indicates one of a feeder link timing advance with timingdrift or a feeder link timing advance without timing drift, or theinformation indicates the feeder link timing advance information, andthe feeder link timing advance information indicates the feeder linktiming advance without timing drift; and communicate with the UE basedat least in part on the one or more NTN SIBs.
 17. The apparatus of claim16, wherein the information indicates at least one of an updateperiodicity for the one or more NTN SIBs or one or more transmissionwindows within an update period for the one or more NTN SIBs.
 18. Theapparatus of claim 16, wherein one or more repetitions of an NTN SIB, ofthe one or more NTN SIBs, within an update period, are associated with asame reference time.
 19. The apparatus of claim 16, wherein thereference time for the at least one of the ephemeris information or thefeeder link timing advance information is based at least in part on theparticular downlink transmit timepoint within an update period.
 20. Theapparatus of claim 16, wherein the information indicates at least one ofthe resource allocation or the modulation and coding scheme forobtaining the one or more NTN SIBs.
 21. The apparatus of claim 16,wherein the information indicates an update periodicity for the one ormore NTN SIBs using a parameter type of the SIB.
 22. The apparatus ofclaim 16, wherein the update to the at least one of the ephemerisinformation or the feeder link timing advance information is independentof triggering the system information update procedure.
 23. The apparatusof claim 16, wherein the one or more NTN SIBs include the single NTN SIBthat includes the ephemeris information and the feeder link timingadvance information.
 24. The apparatus of claim 16, wherein theinformation indicates the feeder link timing advance information, andthe feeder link timing advance information indicates the feeder linktiming advance without timing drift.
 25. The apparatus of claim 16,wherein the feeder link timing advance information indicates the feederlink timing advance without timing drift, and wherein the informationindicates at least one of an update periodicity for the feeder linktiming advance information or an update period for the feeder linktiming advance information.
 26. The apparatus of claim 16, wherein thefeeder link timing advance information indicates the feeder link timingadvance without timing drift, and wherein an application time of thefeeder link timing advance information is based at least in part on alast slot number of a first physical downlink shared channelcommunication of the one or more NTN SIBs or a last slot number of afirst transmission window in an update period, and a system schedulingoffset value.
 27. The apparatus of claim 16, further comprising: atransmitter configured to transmit the SIB and the one or more NTN SIBs,wherein the apparatus is configured as an entity of the NTN.
 28. Amethod of wireless communication at a user equipment (UE), comprising:obtaining, from an entity of a non-terrestrial network (NTN), a systeminformation block (SIB) that indicates information relating to one ormore NTN SIBs that are to include at least one of ephemeris informationor feeder link timing advance information; obtaining, from the entity ofthe NTN, the one or more NTN SIBs based at least in part on theinformation, wherein at least one of: a reference time for the at leastone of the ephemeris information or the feeder link timing advanceinformation to be included in the one or more NTN SIBs is based at leastin part on a particular downlink transmit timepoint, the informationindicates at least one of a resource allocation for obtaining the one ormore NTN SIBs, a modulation and coding scheme for obtaining the one ormore NTN SIBs, a message size of the one or more NTN SIBs, a validityduration of the one or more NTN SIBs, or an accuracy of the one or moreNTN SIBs, an update to the at least one of the ephemeris information orthe feeder link timing advance information is independent of triggeringa system information update procedure, the one or more NTN SIBs includea single NTN SIB that includes the ephemeris information and the feederlink timing advance information, the feeder link timing advanceinformation indicates one of a feeder link timing advance with timingdrift or a feeder link timing advance without timing drift, or theinformation indicates the feeder link timing advance information, andthe feeder link timing advance information indicates the feeder linktiming advance without timing drift; and communicating with the entityof the NTN based at least in part on the one or more NTN SIBs.
 29. Themethod of claim 28, wherein the reference time for the at least one ofthe ephemeris information or the feeder link timing advance informationis based at least in part on the particular downlink transmit timepointwithin an update period.
 30. The method of claim 28, wherein the updateto the at least one of the ephemeris information or the feeder linktiming advance information is independent of triggering the systeminformation update procedure.